Home
Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
z/OS considerations for HCL Launch
HCL Launch includes support for the z/OS platform. Although the articles in this Knowledge Center for using HCL Launch to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
Installing the z/OS® agent
Before you deploy to the IBM® z/OS® platform, you must install the z/OS agent and configure the z/OS server for communication with HCL Launch. If the build process runs on a different logical partition (LPAR), then you must additionally install the agent on the build LPAR. You can install the z/OS agent and deployment tools by using the IBM System Modification Program Extended (SMP/E) or by extracting archive files to the z/OS UNIX™ file system.

Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
- Integrating with HCL OneTest
  When you use OneTest™ Performance, you can create tests and run those tests in HCL Launch by using the HCL OneTest™ Performance Launch plugin.
- z/OS considerations for HCL Launch
  HCL Launch includes support for the z/OS platform. Although the articles in this Knowledge Center for using HCL Launch to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
  - Installing the z/OS® agent
    Before you deploy to the IBM® z/OS® platform, you must install the z/OS agent and configure the z/OS server for communication with HCL Launch. If the build process runs on a different logical partition (LPAR), then you must additionally install the agent on the build LPAR. You can install the z/OS agent and deployment tools by using the IBM System Modification Program Extended (SMP/E) or by extracting archive files to the z/OS UNIX™ file system.
    - Deploying by using the Job Monitor
      You use the Job Monitor to submit jobs and to monitor the job status in your deployment. You must ensure that you have a Job Monitor task running and that you run the HCL Launch process to submit or to monitor the job. Then, you must set up Job Monitor connection properties in your HCL Launch environment.
    - Installing binary and config to different directories
      By default, the agent installer installs the binary and config files into the same directory. You can customize the installation so that these files are installed into different directories. Also, multiple agent configurations can share the same copy of binary files which makes security control and product upgrading easier.
  - Upgrading z/OS® agents
    You can upgrade IBM® z/OS® agents. However, you must upgrade the server before you upgrade the agents.
  - Starting z/OS agents from the z/OS UNIX command line
    The z/OS agent can be started from ISPF as a started task or from the z/OS UNIX command line. To start an agent from ISPF as a started task refer to install/topics/run_agent.html. To start the z/OS agent from the z/OS UNIX command line, follow this procedure.
  - Installing the z/OS® agent and deployment tools by using SMP/E
    IBM® System Modification Program/Extended (SMP/E) is a tool for installing and maintaining software on z/OS® systems. SMP/E controls software changes at the element level. Job Control Language (JCL) is submitted by using 3270 emulation.
  - Job Monitor customization
    The Job Monitor binary is installed with the IBM® z/OS® deployment tools in the hlq.SBUZAUTH data set. You need the assistance of a security administrator and a TCP/IP administrator to complete this customization task.
  - Planning storage
    You can store the versions in CodeStation or in Artifactory/Nexus. To store versions in Artifactory or Nexus, the artifactory details must be passed to the buztool.sh. Every z/OS agent that is used to deploy projects, stores backups of old artifacts so that a rollback can be done when required. Plan the agent directory to ensure there is sufficient space for backup.
  - Customizing and verifying the TSO-ISPF client gateway
    HCL Launch uses the IBM® z/OS® Time Sharing Option-Interactive System Productivity Facility (TSO-ISPF) gateway when it imports and deploys component versions.
- Deploying components to the z/OS® platform
  Use the toolkit to deploy to the IBM® z/OS® platform.

Installing the z/OS® agent

Before you deploy to the IBM® z/OS® platform, you must install the z/OS® agent and configure the z/OS® server for communication with HCL Launch. If the build process runs on a different logical partition (LPAR), then you must additionally install the agent on the build LPAR. You can install the z/OS® agent and deployment tools by using the IBM® System Modification Program Extended (SMP/E) or by extracting archive files to the z/OS® UNIX™ file system.

Note: Beginning with version 6.2.4. the z/OS® deployment tools have become part of the z/OS® agent. The deployment tools no longer require a separate installation. If you are upgrading from a version earlier than 6.2.4, see Upgrading IBM z/OS agents for details about the changes.

Before you begin

Review the system requirements, and then plan the installation:

Review Planning storage.
Review Security requirements on IBM z/OS computers.
Review Customizing and verifying the TSO-ISPF client gateway.
Review Installing the binary and config files to different directories.

Procedure

To install the agent by using SMP/E, complete these steps:
1. Install the z/OS® agent by using SMP/E. See Installing the z/OS agent and deployment tools by using SMP/E.
2. Install agents from the command line. See Installing agents from the command line, and start with step 3.
To install by extracting files to the z/OS® UNIX™ file system, see Installing agents from the command line.